Skip to content

docs(integrations): say that mcp records tool arguments and results by default - #68

Merged
aikins01 merged 1 commit into
mainfrom
docs/integrations/mcp-payloads-default
Nov 10, 2026
Merged

aikins01 merged 1 commit into
mainfrom
docs/integrations/mcp-payloads-default

Conversation

@aikins01

Copy link
Copy Markdown
Contributor

The MCP integration page now says that @telemetry-dev/mcp 0.3.0 records tool arguments and tool results by default, including a result marked isError (telemetry-dev/telemetry#219). Before, the page said payload capture was off by default and showed how to turn it on with capturePayloads: true.

The payload capture section lists what keeps tool content out: captureInput: false drops the arguments, captureOutput: false drops the result, mask and maxAttributeLength apply to both, and capturePayloads: false keeps tool content out of one transport. It also says that error codes and the JSON-RPC error message are recorded with every setting, without the mask. The options table gives the new default, and the page notes that versions before 0.3.0 capture payloads only with capturePayloads: true.

Control payload capture section

Tests: pnpm test.

…y default

@telemetry-dev/mcp 0.3.0 records tool arguments and results, failed
results included, unless captureInput, captureOutput, or
capturePayloads: false keeps them out.
@aikins01 aikins01 self-assigned this Nov 10, 2026
@aikins01
aikins01 merged commit f34684f into main Nov 10, 2026
1 check passed
@aikins01
aikins01 deleted the docs/integrations/mcp-payloads-default branch November 10, 2026 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant